How Microsoft Vaporized a Trillion Dollars, Pt. 6

How Microsoft Vaporized a Trillion Dollars, Pt. 6 Source: https://isolveproblems.substack.com/p/how-microsoft-vaporized-a-trillion-b73

(Continued from Part 5)

Over the following months, with the patterns I had documented — agent sprawl and testing gaps, the continuous influx of crashes, the security surface in foundational services, and the repeated preference for short-term mitigations over structural fixes — all becoming increasingly difficult to contain at the working level, I extended my concerns upward.

On November 19, 2024, I sent a detailed letter to the Executive Vice President of Cloud + AI.

It laid out the technical findings in full, referenced the leadership gaps I had observed, and included concrete proposals for addressing the root causes.

On January 7, 2025 — still months before any public indication of strain in the OpenAI relationship — I sent a more concise executive summary to the CEO.

The letter opened with the potential risks to national security and to Microsoft’s core business, then followed with a compact set of bullets summarizing the key issues in the Azure node stack and the organizational challenges I had seen.

It also noted that I stood ready to help lead a first-principles reconstruction of the Azure node management layer, if given the opportunity in the right capacity.

When those communications produced no acknowledgment, I took the customary step of writing to the Board through the corporate secretary.

That letter referenced the lack of response to the earlier messages, attached the communication sent to the CEO, and observed that the quasi-loss of OpenAI and the related issues appeared preventable given the advance warnings.

In the months that followed, I received no reply — not a single acknowledgment, question, request for clarification, or confirmation of receipt — from the EVP, the CEO, or the Board.

This complete absence of any feedback added its own dimension.

The issues had been surfaced in calibrated, good-faith communications well in advance of visible customer shifts.

Public optimism around Azure capabilities and strategic commitments continued at full pace. Yet the ground-level signals simply produced silence.

The series began with a single engineer’s shock on his first day back in the organization.

It ends with the same observation, now seen at every layer: the foundational problems in the node stack were visible, the operational and security consequences were measurable, and the proposed paths forward were concrete.

At no level did those signals generate a response.

The hoofbeats I mentioned in the previous installment had become audible far beyond the Azure Core buildings on the West Campus.

Whether they were heard at the top remains unknown.

###